Exchange 2010  - CAS site failover issue

Hello, I have subsequent issue:

Though all Exchange 2010 forums are closed I my question in this Exchange 2013 forum - sorry.

I have two active directory sites (Site A, Site B), in both site I have a CAS, HT (on same server) and MBX (on separate server). All servers are EX2010 SP3 on Windows Server 2008 R2. The two MBX servers are DAG members and each CAS is a member of a "one node CAS Array" (casarrayA, casarrayB). For testing I have only one Mailboxdatabase (DB1) where the rccclientaccessserver value is set to casarrayA.

When I check the Outlook connection state (for a user who is in DB1 and DB1 is active in site A) I can see that Outlook connects to casarrayA (according to ccclientaccessserver value). When I perform a DB failover to the MBX server in site B everything works fine for the client. But when I check the Outlook connection state I see that it connects to casarrayB (though the ccclientaccessserver value is set to casarrayA - I doublechecked it). Doing again a failover, the Outlooks connects back to the casaarray in the site, where the DB is active.

I have in mind that Outlook ALLWAYS connects to the the CAS or casaraay specified in ccclientaccessserver value. Is the above mentioned behaviour by design? How can I control (force) that Outlook ALWAYS connects the the CAS set through the rccclientaccessserver value?

Many thanks in advance
Lars

July 5th, 2013 3:56am


I have in mind that Outlook ALLWAYS connects to the the CAS or casaraay specified in ccclientaccessserver value. Is the above mentioned behaviour by design? How can I control (force) that Outlook ALWAYS connects the the CAS set through the rccclientaccessserver value?

Many thanks in advance
Lars


Hi,
That was true until Exchange 2010 SP2 RU3 came out.
In that rollup things changed and you can read about that in the below blog post.

RPC Client Access Cross-Site Connectivity Changes
http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx


In short... if you want to have the old configuration back, just change the value for AllowCrossSiteRpcClientAccess configured on the DAG from "False" to "True"
Was changed in SP2 RU3.


PS. The Exchange 2010 Forum is not closed but maybe a bit harder to find after the new forum "design".



Free Windows Admin Tool Kit Click here and download it now
July 5th, 2013 4:26am

Hi Martina,

I am gonne check it.

Thanks in Advance

Lars

July 5th, 2013 4:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics